Why a receipt has to be recorded in the ledger
The bank balance moves the moment a customer pays, but the ledger shows the money only once an entry records it. Until then the invoice stays open in the receivables listing, the cash account understates what the company holds, and the period-end accounts receivable reconciliation shows a balance the customer no longer owes. The posted receipt is also the ledger side of the comparison a bank reconciliation performs later: the statement shows money arriving, and the entry says what the company did with it.
How a customer receipt is posted
- Read the movement and fix its date. The trigger is a payment that has arrived: a bank credit, a card settlement or a collection recorded operationally. The entry belongs to the date the money moved, not the day someone notices it.
- Debit cash or bank for what arrived. The debit carries the net amount the account received, the figure a bank statement can be compared against later.
- Record supported deductions separately. A documented bank fee, valid withholding or approved discount has its own treatment and account. A deduction merely claimed by the customer is investigated; it does not automatically clear the receivable.
- Credit the receivable for the amount settled. The credit reduces the customer balance by the applied amount. A partial payment leaves the remainder open. If allocation is pending, the receipt can be recorded in the designated temporary account until supporting evidence identifies its destination.
Cash posting example: a receipt with a bank fee withheld
Ashgrove Foods invoices Pellham Distribution USD 24,800 on invoice 4471.
Pellham pays by bank transfer, the bank withholds a fee of USD 62, and USD 24,738 reaches the account. The figures are illustrative and in US dollars; the agreement makes Ashgrove responsible for the bank fee.
The entry has three lines: debit bank USD 24,738 for the money received, debit bank fee expense USD 62 for the charge the bank kept, and credit accounts receivable USD 24,800.
| Account | Debit | Credit |
|---|---|---|
| Bank | USD 24,738 | |
| Bank fee expense | USD 62 | |
| Accounts receivable, invoice 4471 | USD 24,800 | |
| Total | USD 24,800 | USD 24,800 |
The two debits add up to the credit: USD 24,738 + USD 62 = USD 24,800, so the entry balances with the amount invoiced.
What reached the bank is the invoice less the fee: USD 24,800 – USD 62 = USD 24,738.
The receivable clears in full even though less arrived than was invoiced, because the fee is a cost of collecting the money, not a reduction of the sale.
Posting records that the customer paid; it does not decide which invoice the payment settles, which belongs to the application step.
One movement, several open invoices
One entry can carry more than one customer balance.
A single receipt can clear several open invoices, and the credit to the receivable is then written as one line per invoice, each carrying the amount that invoice was settled for, adding up to the total credited. The split is decided in the application step, and posting records the split that was chosen.
Posting a receipt before it is applied
A receipt can be posted before anyone knows which invoice it pays. In that case the entry debits bank and credits an unapplied cash account, a temporary balance that keeps the money visible without reducing a specific invoice. When the allocation is confirmed, a second entry debits unapplied cash and credits accounts receivable for each invoice settled. A balance that stays in the temporary account becomes an unapplied payment to investigate, not a figure to absorb at period end.
The date the entry belongs to
A receipt belongs to the period in which the money moved, not to the period in which someone recorded it. A transfer dated the last day of March and entered in April still belongs to March, because that is when the bank balance changed. Recording it only in April misstates the March balances, even if the cumulative amount agrees after the April entry.
Common cash posting errors
Most cash posting errors leave the books balanced but wrong, which is why they tend to surface later in collections or in the bank reconciliation.
- Crediting only the net amount. If the example above credited USD 24,738, the USD 62 fee would stay as a false open balance on invoice 4471.
- Writing off a claimed deduction. A shortfall the customer has not documented is investigated before it leaves the receivable.
- Posting to the wrong period. The entry date follows the movement, as described above.
- Posting the same receipt twice. A retry after a failed transmission or a manual re-entry duplicates the cash.
- Crediting the wrong customer. A payer name that differs from the customer account sends the credit to another balance.
Cash posting vs. cash application and neighboring jobs
Bank reconciliation compares the ledger against the bank statement, and the posted entry supplies the ledger side. An unapplied payment is a receipt that was posted and not yet matched to an open invoice.
A remittance advice declares what the customer is paying and which deductions apply. Cash application decides which invoice the money settles. Cash posting turns that decision into a journal entry in the general ledger.
Cash posting in medical billing
In healthcare revenue cycle management, cash posting, also called payment posting, means recording insurer and patient payments against the claims they pay, together with the contractual adjustments and denials reported in the remittance. The logic is the same, but the open items are claims instead of commercial invoices.
How Simetrik supports cash posting
Posting a net receipt requires a model that distinguishes cash, the receivable settled and any approved fee or adjustment. Simetrik, an AI-native financial control platform, generates journal entries from configured rules using source data organized through data preparation, reconciliation results and operational records, then sends them to the ERP that holds the books. Simetrik adapts to how each entry must be posted in the customer’s system, and the receipts themselves come from its controls over incoming payments, where bank credits are compared with expected collections.
Validation and synchronization status are part of the control: a correctly calculated entry can still fail to reach the ERP. In Simetrik, each entry is validated before synchronization, and the ERP response is checked before the process continues. The transaction, posting version and ERP response remain connected so that a retry does not become a duplicate receipt, and an entry can be reprocessed, voided or resent with a full audit trail. AI can assist with basic posting-model fields; the team approves the model and its accounting rules.