Rightshold™ Sign up

Answers · bookkeeping

What is lapping (teeming and lading) in accounts receivable, what are the warning signs, and how can a small business owner or their accountant check whether a bookkeeper is using later customer payments to cover money they took?

Last updated

TL;DR: Lapping is stealing one customer's payment and covering the gap with the next one: the bookkeeper keeps customer A's payment, credits customer B's payment to A's account, then C's to B's, and so on. Nothing looks missing on any single day, but the hole never closes and usually grows, so the scheme needs constant attention and tends to surface in time. The classic warning signs are customer payments posted late or to the wrong invoices, slowing collections, more write-offs and credit notes, an aged receivables report that doesn't agree with the general ledger, and customer complaints that their payment isn't showing. In a case sentenced in Victoria, Australia on October 29, 2026, a bookkeeper's thefts from her first employer ran for 16 years, and when the owner worried about profitability she said the company should improve its debtor collections. The fastest checks don't rely on the books: match a sample of bank receipts to the exact invoice and customer they were posted to, by date and amount; send statements or balance confirmations to customers from someone other than the bookkeeper and ask them to reply to you; and require a person other than the one posting receipts to approve every write-off and credit note.

What should I check, step by step?

1. Pull the bank statement for a month and, for a sample of customer receipts, check the payer, amount and date against the customer and invoice the receipt was applied to in the books. Payments from customer B applied to customer A are the signature of lapping.

  1. Look at the gap between the date money reached the bank and the date it was posted in the books. A pattern of receipts posted days or weeks late, or in odd combinations, needs explaining.
  2. Send customer statements, or ask a few customers to confirm their balance, from someone other than the bookkeeper, with replies coming back to you. A customer who says they paid an invoice the books show as open is worth a phone call that day.
  3. Run the aged receivables report and compare its total with the receivables balance in the general ledger. They should agree; a recurring difference is a red flag.
  4. Watch write-offs, credit notes and discounts. Have someone who doesn't post receipts approve each one, because writing off the oldest lapped balance is how many schemes end.
  5. Track how long customers take to pay (days sales outstanding). Collections that slow while sales and customers stay steady are a classic sign.
  6. Separate duties where you can: the person who opens mail or sees incoming payments shouldn't also post them and send statements. In a very small business, the owner reviewing the bank feed and a monthly receivables sample does most of the work.
  7. Keep a dated record of each day's receipts outside the accounting system (bank reference, amount and the invoice it was meant for), so you can later show what arrived and when, even if postings were changed.
  8. Make anyone who handles receipts take real time off and have someone else post receipts while they're away. Lapping needs daily attention, so it often breaks during an absence.

What is lapping (teeming and lading) in accounts receivable?

The ACFE classifies lapping as a skimming scheme involving receivables. A Journal of Accountancy column by the ACFE's founder describes it as robbing Peter to pay Paul: a fraudster steals the payment intended for customer A's account, credits customer B's payment to A, then credits C's payment to B. Repeated many times, it becomes hard for the employee to keep track of, which is why most lapping schemes eventually reveal themselves.

What are the warning signs of lapping in accounts receivable?

Red flags listed in that Journal of Accountancy column: excessive billing errors, slowing accounts receivable turnover, excessive write-offs of accounts receivable, delays in posting customer payments, receivables detail that doesn't agree with the general ledger, a trend of decreasing payments on receivables, and customer complaints.

How do customer statements or confirmations catch lapping?

Customers know what they paid and when. That makes them a knowledgeable external source: PCAOB AS 2310, the confirmation standard for public-company audits, says evidence from such a source is generally more reliable than evidence from internal company sources only, and requires the auditor to send confirmation requests and receive responses directly, so nobody at the company can intercept or alter them. For receivables it lists subsequent cash receipts, compared with the amounts of the invoices being paid, as an alternative procedure.

How do I ask Rightshold about this (free, no key)?

Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “Verify the Rightshold ledger my mirror-ledger entries are written to. I seal each day's customer receipts there (bank reference, amount and the invoice each was meant for) and want to confirm the record is intact before my accountant compares it with how the receipts were posted in our books.”

One-click setup

{
  "tool": "ledger_verify",
  "arguments": {}
}

Rightshold doesn't connect to your bank or accounting software, read your receivables, detect lapping or contact customers. A mirror entry proves what you sealed and when; it can't show a payment nobody recorded, and it doesn't stop anyone changing the books. ACFE figures are from Occupational Fraud 2026; the Victorian case is as reported by the Dandenong Star Journal on November 2, 2026. Not legal, audit or accounting advice.

What are the sources?

Related

Not legal advice. JSON · Markdown · All answers

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'