Client Payments & Reconciliation — business view

1. Business Summary

Receives client payments, allocates them to invoices, integrates with SAP both as a cron-driven sync and as an inbound endpoint that creates payments in Transparent from SAP.

2. Business Value

Receivables control, accurate cash application.

3. Users / Stakeholders

Finance.

4. Workflows

• Manual entry — finance enters the payment header and per-invoice line items.
• SAP-driven inbound — SAP posts a payload that creates payment + line items.
• Reconciliation — after invoice sync, balances are validated.

5. Sub-Features

• Auto-allocation per invoice.
• Bank/method mapping.
• Multi-currency.

6. Business Rules

• Required header fields; default payment method (bank transfer).
• Allocation cannot exceed remaining invoice balance.

7. Data Entities

Client Payment, Client Payment Detail, Payment Method, Bank.

8. Entry Points

• Finance payment screens; SAP receive endpoint.

9. Inputs & Outputs

• Inputs: payment data, allocations.
• Outputs: payment records, SAP IDs.

10. Integrations

• SAP.

11. Calculations / Logic

• Remaining balance per invoice.

12. Status Lifecycle

• Created → submitted → scheduled → paid → reconciled.

13. Permissions

• Finance, brand-scoped.

14. Reports & KPIs

• DSO, allocation gaps.

15. Risks & Observations

• Inbound endpoint relies on basic auth; over-allocation enforced only in business logic, not the data layer.

16. Source Code Evidence

• app/Plugin/finance/Model/{ClientPayment, ClientPaymentDetail}.php.
• app/Controller/SapController.php.