Explain the gap between certified bills and bank receipts
Compare approaches
TL;DR — what you’ll learn
- Reconcile certified amounts, recorded receivables, remittance allocations and bank receipts as distinct records.
- Explain each difference with evidence; do not label an unexplained balance as retention or a deduction.
- Keep unapplied cash visible when the client's allocation is uncertain.
- Link existing payments to the correct invoices without creating a second bank movement.
The client has certified two bills, but the bank receipt is smaller than their combined value. The project dashboard calls the difference a deduction. Finance cannot find a deduction statement, and the client has not confirmed which bill the payment settles. The arithmetic is correct; the explanation is premature.
Build a reconciliation that separates certification, invoice or receivable recognition, cash receipt and allocation. The difference becomes a set of specific questions with owners. It should not become an accounting adjustment simply because the dashboard needs every balance assigned to a category.
Illustrative same-basis figures with no other adjustments. The ₹4 lakh difference is unexplained until evidence supports its classification.
Read the visual as text
Recorded receivables: ₹22 lakh. Certificates of ₹10 lakh and ₹12 lakh linked to ledger records. Existing bank receipt: ₹18 lakh. Allocate only with evidence or an authorised documented policy. Unsettled difference: ₹4 lakh. Not automatically retention or a deduction.
Original explanatory visual: NextEdge Labs. Illustrative records, not client results.
- STEP 01Align the comparison basis
Owner: Billing and finance
Link certificates, receivables, currency and dates.
- STEP 02Identify cash and remittance
Owner: Finance
Verify existing receipt and allocation evidence.
- STEP 03Review differences and allocations
Owner: Finance and commercial owners
Keep disputed adjustments and unapplied cash visible.
- STEP 04Reconcile and follow up
Owner: Receivables owner
Verify balances and assign remaining questions.
Review and apply the existing payment to the correct records.
Retain unapplied cash or the documented policy allocation with its limitation.
Return path: Obtain remittance evidence, correct the allocation and reconcile without creating another bank movement.
Read the workflow as text
1. Align the comparison basis (Billing and finance) → 2. Identify cash and remittance (Finance) → 3. Review differences and allocations (Finance and commercial owners) → 4. Reconcile and follow up (Receivables owner). After step 2, ask: Is the bill-level allocation supported? Yes: Review and apply the existing payment to the correct records. No: Retain unapplied cash or the documented policy allocation with its limitation. Return: Obtain remittance evidence, correct the allocation and reconcile without creating another bank movement.
Workflow: NextEdge Labs. Apply the project’s actual authority and procedures.
Establish the basis of the comparison
Identify the contract, client entity, billing period, certificate, associated invoice or receivable record, currency and bank receipt. Check whether the certificate figure is gross, net or already adjusted for specific items. Compare like bases before subtracting one total from another.
Certification and accounting recognition are related but not necessarily identical events. Finance determines the actual treatment under the contract and accounting policy. Preserve the certificate as evidence and link it to the relevant ledger records rather than assuming that every certificate is already a posted invoice.
Keep dates separate: application, certification, invoice, contractual due date, bank value date and allocation date. They answer different questions. A receipt after the reporting cut-off should not silently reduce the historical outstanding position for an earlier date.
Reconcile twenty-two lakh with eighteen lakh
In this fictional example, two certificates show ₹10 lakh and ₹12 lakh on the same comparable basis. The associated recorded receivables total ₹22 lakh. The bank has received ₹18 lakh, with no other adjustments in the example. The simple unsettled difference is ₹4 lakh.
If the client's verified remittance allocates ₹10 lakh to the first bill and ₹8 lakh to the second, the first is settled and ₹4 lakh remains against the second. Record that allocation and its evidence. It is not a new cash receipt; it explains the existing ₹18 lakh.
If no reliable allocation is available, keep the cash as received but unapplied or allocated only under an authorised, documented policy. Do not claim that the second bill is specifically short by ₹4 lakh merely because a first-in-first-out rule produced that result. The overall balance is known; the bill-level explanation may still be unresolved.
Investigate differences without inventing deductions
Possible explanations include timing, a disputed item, retention, advance recovery, an agreed adjustment, tax-related withholding or an allocation error. These are investigation categories, not conclusions. Each requires the relevant certificate, remittance, contract, correspondence or finance evidence.
Show claimed by client, verified and disputed amounts separately where needed. A deduction shown in a remittance does not automatically mean the contractor accepts it. The commercial owner may need to investigate while finance records the appropriate position under policy.
Do not use a universal tax rate or retention percentage to fill a gap. Applicable treatment depends on the actual transaction and terms. An unexplained ₹4 lakh should remain an explicit reconciliation exception until the evidence supports a more specific classification.
Allocate existing cash carefully
ERPNext's Payment Reconciliation documentation describes linking existing submitted payments to outstanding invoices, with company, party and account checks. It distinguishes allocation from creating another bank movement. That is the operational boundary to preserve when designing the reconciliation process.
Check the payment's available unallocated amount before applying it. One receipt may cover several invoices, and one invoice may be settled by several receipts. The allocation table should reconcile to both sides and prevent the same cash from being used twice.
Some systems can propose first-in-first-out allocations. Treat such proposals according to the organisation's authorised policy and available remittance evidence. Review the bill references before acceptance, especially where the client has expressly identified a different allocation.
Preserve reversals and revised certificates
A client may revise a certificate, issue a later adjustment or reverse an earlier allocation. Keep the original record and link the revision. Do not overwrite the earlier figure so that last month's reconciliation can no longer be explained.
If a bank receipt is reversed, finance must record and reconcile the actual bank event through the approved process. An allocation correction alone should not invent or remove cash. Separate changes to the cash record from changes to which invoices that cash settles.
For a credit or agreed adjustment, verify the document, authority and affected balance. Check that it has not already been reflected in the net certificate or another ledger entry. Counting the same adjustment twice can make a short payment appear fully explained while understating the amount still due.
Give the exception to the right owner
Finance owns bank and ledger reconciliation. Billing or commercial teams obtain certificate and remittance explanations and pursue disputed deductions. The project team supplies supporting performance or measurement evidence where required. Assign a named person to each unresolved item rather than one broad accounts follow-up label.
A useful review shows the remaining amount, reason or unknown status, latest correspondence, next action and expected decision date. Keep cash received but unapplied visible alongside unpaid receivables. Otherwise collection teams may chase money that has already arrived while overlooking the allocation work.
Track age from the relevant event, not merely from the date the exception was entered. A newly created row can represent a long-standing issue. Preserve original dates so management sees the actual delay in resolution.
Test the bridge through a reporting period
Use the ₹22 lakh and ₹18 lakh example, then add a partial remittance explanation, a revised certificate and a reversed allocation. At each stage, reconcile certificate basis, recorded receivable, cash, allocations and remaining balance. Have another finance reviewer reproduce the result from the saved evidence.
A controlled register may be adequate when volumes are low and ledger links are reliable. Native reconciliation is preferable when the ERP already holds the relevant transactions. Automation can propose references or extract remittance lines, but it should not convert an unexplained difference into an approved write-off.
The useful result is an outstanding position the collection and project teams can act on. It tells them which money is missing, which money is merely unapplied and which adjustment still needs a decision.
- Put certificates, ledger records, remittances and bank receipts on a consistent basis.
- Reconcile the total before assigning bill-level explanations.
- Obtain evidence for deductions and approve allocations of existing cash.
- Review unresolved and unapplied balances with named finance and commercial owners.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
References and further reading
Sources checked 15 October 2026. The worked examples and diagrams are original editorial explanations, not client results.
- ERPNext — Payment ReconciliationBefore you begin; allocation and verification
Allocation of existing payments, not another bank movement.
Visual credits
Original explanatory visuals and workflow diagrams by NextEdge Labs. Labels and text equivalents are included in the page. Numerical scenarios are illustrative; diagrams preserve the project owner’s approval and exception decisions.