Recording Payments

Overview

Recording payments keeps invoice balances, customer history, and receipts accurate. Payments may come through an online processor when configured, or they may need to be recorded by staff when money is received through another approved method.

Business Value and Typical Use Cases

Record a cash, check, terminal, or external payment according to your process.
Confirm that an online payment has updated the invoice.
Close an unpaid invoice after payment is received.
Prepare customer receipts and daily reconciliation.

Before You Begin

Confirm you can log in to OneSuite and access the module described in this article.
Make sure your organization has completed any required setup, such as license activation, user permissions, payment settings, or connected email accounts.
Use production records or approved test records when learning a workflow so you do not accidentally change live customer information.

Prerequisites and Permissions

Active OneSuite installation or trial.
User account with the appropriate role or permission.
Current production release interface.
Stable browser session.

Concepts

Payments and invoicing turn customer work into billable records. An invoice explains what the customer owes, why they owe it, when it is due, and how they can pay. Payment records and receipts then complete the billing history. A good invoicing process connects customers, products or services, taxes, discounts, online payment links, payment history, and receipts into one reliable workflow.

How This Feature Fits Into OneSuite

Payments connect directly to invoices, customers, receipts, payment history, and reporting. A payment should always be reviewed in the context of the customer and the invoice or transaction it belongs to.

Products and services may originate from the OneSuite/WooCommerce commerce foundation where configured. This allows catalog information to support POS and invoice line-item workflows without forcing staff to recreate the same sellable item repeatedly.

Screen Orientation

Payments documentation should be read as part of the complete billing lifecycle: identify the customer, create or locate the invoice, present the amount due, receive or record payment, issue the appropriate receipt, and confirm the customer history reflects the outcome.

Do not treat payment status and invoice status as interchangeable. One describes the state of the billing document and the other describes money received or still due. Review both when reconciling customer balances.

Before using online payment functions, confirm the required payment provider connection and organization settings are complete. Staff should never improvise payment configuration during a live customer transaction.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

Billing staff create and review invoices, collect or record payments, and confirm receipts and payment history.
Managers review exceptions, aging, failed or incomplete workflows, and daily billing activity rather than editing every transaction themselves.
Administrators maintain payment-provider configuration, user permissions, and company-level settings that billing workflows depend on.

Step-by-Step Instructions

Open Payments and locate the invoice.
Confirm customer name, invoice number, balance, and payment amount before recording anything.
Select the available Record Payment, Add Payment, Mark Paid, or payment action.
Enter payment amount, date, method, reference, and notes where available.
Save the payment.
Verify that the invoice balance or status changed correctly.
Open payment history or receipts to confirm the payment is visible.

Expected Results

When completed, the record, action, or workflow described in this guide should be visible in OneSuite, searchable from the appropriate module, and connected to the related customer, company, invoice, payment, communication, or activity history where applicable.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.

Business Workflow

Payment received → Invoice opened → Amount verified → Payment recorded → Status updated → Receipt issued → Daily reconciliation reviewed.

Real-World Business Scenarios

No additional role-specific guidance is required for this topic.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Record payments immediately after receipt.
Use references for checks, terminal transactions, or external confirmations.
Avoid marking invoices paid without proof.
Review payment history daily.

Common Mistakes

Recording payment on the wrong invoice.
Entering the total instead of partial amount.
Failing to add reference notes.
Recording a duplicate payment after online payment already posted.

Troubleshooting

Symptom: the page or button is not visible. Cause: your role may not include access to this module or the current license may not include the feature. Solution: ask an administrator to review your role, workspace access, and license status. Verification: sign out, sign back in, and confirm the menu item appears.
Symptom: a saved record cannot be found. Cause: filters, search terms, ownership, or status views may hide records. Solution: clear filters, search by name, email, phone, invoice number, or company, and check active versus archived views. Verification: open the record and confirm the latest information appears.
Symptom: a workflow stops before completion. Cause: required fields, connected account setup, payment configuration, or missing customer details may be incomplete. Solution: review the required fields shown on the page and complete setup items before retrying. Verification: repeat the step and confirm the expected success message or updated status appears.

Frequently Asked Questions

Can I record partial payments?: Use the available payment amount fields if supported in production.
What if payment was recorded wrong?: Follow your organization’s correction process.
Where can I verify payment?: Check invoice status, payment history, and receipts.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion