How to Correct a Saved Service Payment

Edited receipts erase what was actually collected

If the person who took the cash can change the amount later, the firm cannot tell what was received on the day. A deleted row is worse: the UTR disappears and a duplicate warning can never fire for that reference again.

A correction done in a side chat has no reason, so the next person does not know whether the amount, the job, or the mode was wrong.

A one-person firm still needs a trail. Skipping approval because there is nobody else to ask leaves the original and the replacement as two unexplained rows.

Why this happens

• The saved payment is edited in place.
• The payment is deleted to hide a mistake.
• A correction is requested with no reason.
• The owner rejects the request and does not leave a note.

Biznsbook addresses this through Correction with a reason, reverse and replace, owner audit trail when Service Billing & Collections is licensed. Clients are parties you already keep. A collector records the amount without seeing the fee or the outstanding.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Correct a Saved Service Payment

Built for owners and collectors who record service jobs and client payments in Biznsbook Collections.

1. Leave the saved payment as it is. Collectors and owners do not edit or delete a payment. My entries can show the row. The amount on that row stays the amount that was typed.
2. Request a correction with a reason. From the collector’s own entry, Request correction needs a reason. The collector does not see the approval queue and does not see fees or outstanding while asking.
3. Open Corrections. The owner uses the Corrections queue. Approve to reverse the original and write the new entry when a replacement is needed. Reject with a note when the original should stand.
4. Read the chain on the payment. Open the payment to see who entered it, the allocation, and the chain from the original through the request to the replacement. The original is never overwritten.
5. A one-person firm can self-approve. The same person may approve their own request. The reason and the trail remain. Self-approval does not delete the first row.
6. Allocate the replacement if the jobs changed. If the new entry must sit on different jobs, use Allocate after approval. The parts must still add up to that payment. If ledger posting is on, the reversal and the new payment post quietly. The collector does not see that journal.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen names in this guide match Collections in the product: Record a payment, My entries, Dashboard, Jobs, Payments, Corrections, Service types, and Settings.

Common mistakes to avoid

• Mistake 1: The saved payment is edited in place. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 2: The payment is deleted to hide a mistake. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 3: A correction is requested with no reason. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 4: The owner rejects the request and does not leave a note. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

• Leave the saved payment as it is — Collectors and owners do not edit or delete a payment.
• Request a correction with a reason — From the collector’s own entry, Request correction needs a reason.
• Open Corrections — The owner uses the Corrections queue.
• Read the chain on the payment — Open the payment to see who entered it, the allocation, and the chain from the original through the request to the replacement.
• A one-person firm can self-approve — The same person may approve their own request.

Teams that leave an undecided fee blank, require a reference on non-cash payments, and correct by reversal instead of editing the row keep the period totals and the trail intact.

How Biznsbook supports this workflow

Correction with a reason is documented in Biznsbook Service Billing & Collections capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

reverse and replace is documented in Biznsbook Service Billing & Collections capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

owner audit trail is documented in Biznsbook Service Billing & Collections capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

Ledger posting is off until Collections settings turn it on, and only when Accounting or Finance is licensed. Outstanding is the fee plus any tax, minus the payments on the job. Collectors do not see fees, outstanding, other people’s entries, the dashboard, statements, the correction queue, or a journal.

Suggested implementation timeline

1. Week 1: Document current process gaps and configure Correction with a reason with finance owner sign-off.
2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
5. Ongoing: Monthly review using the trail is the record and leadership dashboard.

Related guides

Start with track a service job and fee, then record a client payment and allocate a payment across jobs.

Product page: Service Billing & Collections. Clients are parties: CRM. Corrections: correct a saved payment.

Request, approve, or reject

The person who recorded the payment requests the correction and must give a reason. They still cannot edit or delete the row, and they still cannot see fees, outstanding, other people’s entries, or the queue.

The owner approves or rejects. Approve reverses the original and writes the new entry when a replacement is needed. Reject requires a note. A one-person firm can approve their own request. The reason remains either way.

What you can still see afterward

Open the payment for who entered it, the allocation, and the chain from the original through the request to the replacement. My entries for the collector still lists the amount they typed. It does not become a view of the firm’s outstanding. My entries continues to show that collector only their own rows for today or this week.

If the replacement should be split, allocate it after approval. The parts must add up to the new payment. Opening credit and opening balance jobs stay as the owner recorded them unless the owner records a different opening credit on purpose. Settings still apply after a correction: non-cash payments need a reference when that setting is on, and the phone in client search stays as the owner left it. The dashboard then follows the payments that remain active, including collections by mode and by the person who entered them. Clients who still owe money stay on the owner dashboard only.

Metrics to track monthly

• Billed for the date range
• Collected for the date range
• Outstanding
• Collections by payment mode
• Collections by the person who entered them

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook Correction with a reason and related capabilities.

The trail is the record

Approval reverses the original and writes a new entry when one is needed. The original stays visible. Outstanding follows the payments that are still active. If the owner has turned ledger posting on, the reversal and the replacement post in the background and stay off the collector screen.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

How this differs by industry