Appearance
Allocate Payments
Application address: /accounting/allocate-payments · Product baseline: 0.4.0
Reference status
Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.
Open this screen
Use OSERP navigation to find Allocate Payments, or open /accounting/allocate-payments on your OSERP application after signing in. Confirm the active company before reading or changing records.
Menu access: accounting:read
Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.
Fields and input controls
Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.
Select all shown
| Property | Reference |
|---|---|
| Reference key | select-all-shown |
| Location | Screen / contextual panel |
| Input control | checkbox |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Interface explanation | Select all shown |
| Editing | No disabled/read-only condition declared directly on this control. |
Find a document, reference or amount
| Property | Reference |
|---|---|
| Reference key | find-a-document-reference-or-amount |
| Location | Screen / contextual panel |
| Input control | search |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | Find a document, reference or amount |
| Editing | No disabled/read-only condition declared directly on this control. |
Amount
| Property | Reference |
|---|---|
| Reference key | amount |
| Location | Screen / contextual panel |
| Input control | number |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Minimum | 0 |
| Input increment | 0.01 |
| Editing | No disabled/read-only condition declared directly on this control. |
Date
| Property | Reference |
|---|---|
| Reference key | date |
| Location | Screen / contextual panel |
| Input control | date |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Reference
| Property | Reference |
|---|---|
| Reference key | reference |
| Location | Screen / contextual panel |
| Input control | input |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | UTR, cheque no, advice |
| Editing | No disabled/read-only condition declared directly on this control. |
Search name, code, phone or email
| Property | Reference |
|---|---|
| Reference key | search-name-code-phone-or-email |
| Location | Screen / contextual panel |
| Input control | EntityPicker |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | Search name, code, phone or email |
| Editing | No disabled/read-only condition declared directly on this control. |
Named actions
These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.
- Use this
- Cancel
- Record
- Clear selection
Help text and messages
The following wording is embedded in this screen. It describes interface guidance, rather than independently verified system guarantees.
- Match what customers have paid against the invoices it settles.
- Match what has been paid to suppliers against the bills it settles.
- Match what a courier has remitted against the cash-on-delivery orders they collected it for.
- Money that settles no particular invoice — a deposit, an overpayment, or one round figure against the account. It is held as an advance until you apply it.
Verification still required
Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.
See the operating manual, coverage register, and troubleshooting guide.