Applying Payments

Applying a payment reduces an invoice balance after money has been received or confirmed. This is a Billing workflow because it updates the receivable.

It is not the same as provider settlement, bank reconciliation, wallet funding, or outbound payout execution. Those belong to Payments & Settlement.

It is also not the same as agriculture settlement payout. If the organisation is paying a farmer, worker, transporter, supplier, or group leader, that is an outbound payment flow and belongs to shared Payments even when Agriculture produced the supporting source evidence.

Open Billing -> Operations -> Invoices, find the invoice, then use Apply Payment from the invoice action or detail area where available.

Workspace Reference

Area	What The User Does
Invoice list	Finds the invoice by party, invoice number, reference, status, or balance.
Invoice detail	Confirms lines, balance, allocations, credit notes, write-offs, and posting status before applying money.
Apply Payment	Opens the payment allocation form.
Payment history	Shows previous allocations and helps avoid duplicates.
Aging and statements	Shows the remaining receivable after the allocation.

When To Apply A Payment

Apply a payment when:

• a customer has paid an invoice
• a receipt needs to be allocated against one or more invoices
• a partial payment should reduce an outstanding balance
• a payment reference should appear on invoice history
• a statement should show the receipt against the party

Do not create a new invoice to record a receipt. Apply the payment to the existing invoice.

Apply Billing payments only when a party owed the organisation money on an invoice. Do not use this workflow to settle producer statements, wages, labour claims, or supplier payout batches.

Payment Form Details

The payment form usually captures:

Field	Required	Meaning
Invoice	Yes	Invoice being paid or allocated.
Party	Yes	Customer, member, tenant, supplier, school, buyer, or other billed party.
Payment amount	Yes	Amount received and allocated.
Payment date	Yes	Date used for the payment record.
Currency	Recommended	Currency of the payment.
Payment channel	Yes	How the money was received, such as cash, bank, mobile money, wallet, cheque, card, or internal transfer.
Reference	Recommended	Receipt, provider, bank, cheque, or internal reference.
Narration	Recommended	Notes that explain the receipt.

The available channels depend on tenant setup and permissions.

Before submitting, compare the payment amount with the current invoice balance. If the payment is partial, the invoice remains open for the remaining amount.

Partial Payments

If the amount received is less than the invoice balance, the invoice remains partially paid. The remaining balance continues to appear in aging, statements, and collection follow-up.

Users should confirm that partial payments are intentional and that the narration or reference is clear enough for later review.

Overpayments

If the amount received is greater than the invoice balance, follow organisation policy.

The workflow may:

• block the overpayment
• require manual review
• leave a credit balance for later allocation
• require a refund or adjustment workflow

Do not hide an overpayment by changing the invoice lines unless the invoice itself was wrong and has been corrected through the proper billing process.

Review After Applying Payment

After applying a payment, confirm:

• invoice balance reduced correctly
• payment appears in invoice detail
• party statement reflects the payment
• payment status is clear
• reference and narration are useful
• GL status is posted or pending follow-up as expected
• settlement status is reviewed separately where required

Billing Versus Payments & Settlement

Question	Billing Payment Allocation	Payments & Settlement
Which invoice balance reduced?	Yes	No
Which party owes less after payment?	Yes	No
Which channel moved the money?	Captured for classification	Reviewed in depth.
Did provider, bank, wallet, or till settle correctly?	No	Yes
Are there settlement disputes or exceptions?	No	Yes
Is an outbound payout batch needed?	No	Yes

This separation keeps receivables work clear while still allowing finance to reconcile channels properly.

For agriculture or field-service business stories:

• use Billing payment allocation for buyer or customer receipts against invoices
• use Payments for farmer, worker, or supplier payout execution
• use settlement or report review to reconcile the full business story end-to-end

Accounting Relationship

Billing payment allocation normally reduces receivables and records the received-payment side according to the selected channel and accounting setup.

The payment channel affects whether the receipt is treated as cash, bank, mobile money, wallet, card, cheque, or another accepted rail. Settlement review then confirms whether the channel movement cleared externally.

If accounting fails after payment allocation, review:

• selected channel
• currency
• receivable setup
• cash, bank, wallet, or clearing-account setup
• required sub-ledger or party tracking
• posting approval status

Common Mistakes

Mistake	Better Practice
Applying payment to the wrong invoice.	Search by party and invoice reference before submitting.
Using payment allocation to fix an invoice error.	Use credit note, write-off, or invoice correction workflow where appropriate.
Treating allocation as settlement reconciliation.	Use Payments & Settlement for provider, bank, wallet, till, or processor reconciliation.
Leaving vague references.	Capture receipt, provider, bank, cheque, or internal reference clearly.
Ignoring partial balances.	Review aging and statements after partial payments.
Using invoice allocation for an outbound agriculture payout.	Use payment batches and obligation-backed payout execution instead.

Related Guides

• Invoices
• Aging And Statements
• Payments & Settlement