Customer payments are separate records linked to invoices. Store the amount and payment date rather than overwriting the invoice status with a note that says “paid.”
That separation is what allows an invoice to have several payments while keeping the original billed total intact.
Payment records can include method, reference number, payer name, currency, bank account and clearance status.
Those details are useful when the customer asks about a transfer, Finance has several receipts for the same amount or a payment is still waiting to clear.
If the customer pays only part of the invoice, record the amount received and leave the rest outstanding. Later payments can be added to the same invoice.
The amount paid and amount due can therefore change without creating replacement invoices for every installment.
Invoice payment records can carry the payment currency, conversion information to the invoice currency and a base-currency amount for Accounting.
That helps distinguish what the customer actually paid from the value that the ledger needs to record in the workspace base currency.
A credit can reduce the customer balance, but it is not a payment. Lynka keeps credit allocations and cash receipts as different records.
That makes it possible to explain whether an invoice balance fell because the customer sent money or because the bill was adjusted.
The Payments feature is an invoice-payment ledger inside Lynka. The bank, card processor or other payment method handles the actual transfer.
That boundary is intentional and should remain explicit on the marketing page so “payment tracking” is not mistaken for built-in payment processing.
Customer payment records can reference an internal bank account and accounting journal. Bank reconciliation can then match imported bank activity against customer receipts rather than asking Finance to re-enter the payment just to clear the statement.
If the bank movement does not match confidently, it can remain unresolved for review. Recording a payment and reconciling the bank are related steps, not the same step.
A customer can pay a deposit, another amount after delivery and the final balance later. Each receipt can keep its own date, method, reference, currency and clearance status while the invoice continues to show the total amount paid and the amount still due.
That is more useful than changing one payment field every time another transfer arrives because the individual receipt history remains available.
Payment tracking is accounting for money received, not moving the money itself. Lynka keeps the receipt history beside the invoice no matter which bank or payment method the customer used.
A customer payment can show amount, date, method, reference, payer details, currency, bank account and clearance status.
