Opening Balances and Partial Payments: A Complete Customer Account Example

Why can an account go wrong from its very first number?

Every new transaction may be recorded correctly while the customer's balance remains wrong because the starting point was never verified. An opening balance is the amount outstanding at a specified date before a new period or system begins. If it comes from memory or an unreconciled notebook, every subsequent payment carries that error forward.

What is an opening balance?

It is the account balance at a defined transition point, such as the start of a month or the first day using a new program. It needs a date, direction, currency, and source. “50000” alone is insufficient. Does the customer owe it, or is it owed to the customer? Is it YER or SAR? Does it include a transaction from the morning of the transition? Who checked it?

Choose a clear cutoff. If the old statement ends at the close of July 31, the opening balance on August 1 is the approved closing balance. Do not include August 1 transactions in that opening amount and then record them again, which would duplicate their effect.

How to establish the starting point

Gather the records explaining the balance: an earlier statement, ledger pages, unpaid invoices, receipts, returns, and any reconciliation agreement. Put entries in order up to the cutoff and calculate the balance. If part cannot be verified, mark it “under review” instead of presenting it as final.

Record the following in the migration record:

• The customer name or unique code.
• The cutoff date and time.
• The balance and who owes whom.
• The currency.
• The source amount or document references.
• The people who entered and reviewed it.
• Any outstanding note or dispute.

Keep a copy or reference to the source according to business policy. The purpose is to explain the first line when a customer asks where it came from, rather than accumulate paperwork.

Use a consistent rule for increases and reductions

In this example, “customer owes” means money due to the shop. Credit sales increase that amount; payments and approved returns reduce it. If the account moves into the customer's favor, say so explicitly instead of relying on a negative sign. Another system may use debit and credit or incoming and outgoing terminology, but the meaning must remain consistent.

Include this rule in staff training and the statement explanation. Many errors are not arithmetic mistakes: an employee may put a payment in the column that increases the balance because the field label is unclear.

Example: Al Noor Store's customer account

Suppose reconciliation through July 31 establishes that Al Noor Store owes 84000 YER. The new system starts on August 1 with an opening balance of 84000 YER owed by the customer, supported by the approved migration statement.

The following transactions take place in August:

• August 2: a credit sale of 36000 YER, sale reference 201.
• August 5: a partial payment of 25000 YER, receipt reference 71.
• August 8: an approved return of 7500 YER, linked to the sale reference.
• August 12: a credit sale of 18000 YER, sale reference 214.
• August 15: a partial payment of 40000 YER, receipt reference 89.

No currency conversion is needed: every transaction uses the same currency. Any other currency would need its own balance and transaction path and would not be added to YER.

Calculate the balance step by step

Start with 84000 YER owed by the customer. Add the August 2 sale of 36000 to reach 120000. The August 5 payment reduces it by 25000 to 95000. The August 8 return reduces it by 7500 to 87500. The August 12 sale increases it by 18000 to 105500. The August 15 payment reduces it by 40000, leaving a closing balance of 65500 YER owed by the customer.

Check the result using grouped totals:

• Opening balance: 84000.
• Total new credit sales: 54000.
• Total payments: 65000.
• Total returns: 7500.
• Closing balance: 84000 + 54000 − 65000 − 7500 = 65500 YER owed by the customer.

Detailed entries and grouped totals must produce the same result. If they differ, look for a duplicate, an incorrect sign, or a row outside the period before sending the statement.

Why should the invoice remain unchanged after a payment?

An invoice for 36000 documents the value of a sale. When the customer pays 25000, the sale does not become 11000. The sale remains 36000, the payment appears separately as 25000, and the remainder forms part of the running balance. Editing the original erases the transaction value, may prevent receipt reconciliation, and can alter earlier period reports.

Record each payment with its amount, date, method, and reference. Multiple payments should appear as multiple entries. Both parties can then see the original amount, what was paid, when it was paid, and what remains, rather than an unexplained final number.

How to record a partial payment

Before saving, select the correct customer and currency, enter the amount actually received, and choose the payment method and treasury account or destination where supported. Add a receipt number or clear reference instead of a vague note such as “payment.” A useful description might be “Partial payment toward the account through August 5,” without claiming it closes a specific invoice unless it was formally allocated to that invoice.

After saving, open the statement and confirm that the balance fell rather than rose. Then check the treasury effect if the functions are linked. A customer payment without the corresponding cash effect, or the reverse, creates a discrepancy at closing.

Allocate the payment to an invoice or to the general account?

Some businesses apply payments to the oldest invoice, some follow the customer's specified invoice, and some programs track only an overall balance. Choose a clear policy and do not assume automatic allocation. If the payment is allocated, state the invoice reference. If it is on account, say so, so that a reviewer does not assume a particular invoice is settled.

Either way, payment totals and the balance must remain correct. Allocation helps invoice-aging reports but requires accurate invoice-level information. A general account balance is simpler, but may not answer which invoice remains open.

A return or discount is not a payment

The return in the example reduces the balance, but it is not money received by the shop. It needs its own type and a reference linking it to the sale. An approved discount also reduces the balance because of a documented commercial decision, not a collection. Mixing these with payments can overstate cash receipts or hide the reason for a change.

If goods return to inventory, review the quantity effect under the system in use. Some goods may no longer be saleable, or the application may not link to inventory. Verify and document the procedure instead of assuming the effect.

Correcting the wrong amount or customer

If the 25000 payment was posted to another customer, do not manually alter the closing balance to compensate. Use a correction method that preserves the mistake's history, then post the correct entry with a linking reference. If the system only permits deletion, document why it was deleted and who approved it, and retain the receipt reference before re-entry.

Afterward, review both customer accounts, the treasury account, and the reporting period. An error may be removed from one account while remaining in another report. A successful result on one screen does not establish that the whole correction is complete.

Prepare the statement from the example

The statement starts with the customer details, the August 1–15 period, and currency YER. It shows an opening balance of 84000 owed by the customer, followed by the five entries in order: sale, payment, return, sale, payment. Show the running balance after each row, then totals and the closing balance of 65500 owed by the customer.

Check references 201, 71, the return reference, 214, and 89. If the statement is sent before the end of August 15, state the issue time so later entries are not confused with its contents. Ask the customer to identify the date, reference, and amount of any disputed entry. This turns “the balance is wrong” into something that can be checked.

Reconcile a customer's disagreement

If a customer says their balance is lower, start from the last point both sides agreed on rather than the final figure. Compare the opening balance first, then review entries in order. Request a receipt for any missing payment and check the name, date, currency, and payment method. It may have been posted to a similarly named customer or outside the period.

Create a discrepancy list instead of editing the statement during the discussion. For each difference, record the claim, supporting document, review result, and any required correction. Once agreed, issue a new version and identify it as authoritative. Retain a reference to the previous version under the business's procedure.

Checklist before approving the account

• The cutoff is clear and its transactions are not included twice.
• The name or customer code matches the correct record.
• The balance explicitly states who owes whom.
• The currency is visible and separate from other currencies.
• The opening balance source is retained and reviewable.
• Every credit sale is a separate referenced entry.
• Every partial payment has a separate receipt or reference.
• Returns and discounts are separate from collections.
• Corrections do not rely on manually changing the final balance.
• The running balance is calculated after every entry.
• The grouped totals reproduce the closing balance.
• Payment effects on treasury accounts are checked where relevant.
• The statement identifies its period and issue time.
• Any dispute or provisional figure has an owner and review date.

Common mistakes

• Entering the opening balance from memory.
• Recording it without a currency or direction.
• Including a transition-day transaction in the opening balance and adding it again.
• Changing the sale value when a partial payment arrives.
• Recording a return as money received.
• Assigning a payment to a customer with a similar name.
• Deleting a mistake without a reference or reviewing linked reports.
• Sending a final statement while the starting balance is still disputed.

Frequently asked questions

Is an opening balance new revenue?

No. It carries forward the account's position at the cutoff rather than recording a new sale. Treating it as revenue can count previous transactions again. Keep it clearly described as an opening balance with an identifiable source.

Can the opening balance be zero?

Yes, if reconciliation shows nothing outstanding or the account is new. Do not assume zero for an old account before reviewing its records, because later payments may incorrectly reverse the balance's direction.

Does a partial payment automatically settle the oldest invoice?

That depends on the business policy and software capabilities. Do not assume allocation. Identify the invoice if the payment belongs to it, or clearly record it against the general account.

What if the customer pays more than the balance?

First verify the amount, currency, and customer. If correct, the balance may move into the customer's favor. State this clearly rather than hiding it behind a negative sign, and agree how the credit will be used or refunded.

Can the opening balance be changed after work begins?

A reliable new document may justify a correction, but its reason, date, and effect must be retained through the system's procedure. A silent change makes earlier statements difficult to explain.

Conclusion

The opening balance is a reference point, not a balancing plug, and a partial payment is a transaction, not an invoice edit. Establish the cutoff, source, direction, and currency, then reference every sale, payment, return, and correction. This example starts with 84000 YER and ends with 65500 YER owed by the customer through reproducible entries. When both customer and reviewer can reach the same result step by step, the statement becomes a reconciliation tool rather than simply a demand for a final amount.