A payment-related form must say what its evidence actually establishes
A customer can submit an invoice reference, an amount and a remittance document without the supplier having confirmed that money arrived. Treating those events as equivalent can make an internal screen appear decisive while the underlying evidence is still incomplete.
This guide follows a fictional supplier's invoice follow-up form. Its amount and currency are preserved correctly. The failure is the meaning assigned to an attachment. The investigation separates customer-provided information from an authorised review of settlement evidence, then shows how local presentation and provider capability fit around that distinction.
Define the records before interpreting the status
Invoice I-72 requests 1,250.50 BAM. The form displays the amount in the format approved for its Bosnian audience and retains the invoice reference. A customer attaches advice document A-19 and submits a message saying that a transfer has been initiated.
The receiving screen immediately labels I-72 “Paid”. The staff member reviewing it has not checked a bank record. The attached document itself describes an instruction; it does not establish a credited amount in the supplier's account.
The case contains three different sources:
| Record | What the inspection establishes | What it does not establish |
|---|---|---|
| Form receipt F-41 | Invoice reference I-72, stated amount and attachment A-19 were received | That the stated transfer settled |
| Customer advice A-19 | The customer supplied a document describing a payment instruction | That the supplier's account was credited |
| Authorised bank review B-80 | No matching credit was found in the account and interval actually inspected | That payment can never arrive, or that every account and later interval has been checked |
The last limit matters. Absence in a bounded review is a reason to leave settlement unconfirmed, not a basis for declaring the customer dishonest or the transfer impossible.
Find the rule that produced the misleading conclusion
The form receipt is intact. The investigation then inspects the status transition. A rule sets the invoice to paid whenever the attachment field is non-empty. It does not require a matched credit or an authorised settlement decision.
That establishes a specific cause for this status, distinct from missing data or a failed notification. Renaming the attachment button would not repair the transition. Asking staff to remember that “Paid” sometimes means “document received” would preserve the ambiguity at the point where colleagues rely on the status.
The accounting owner defines the permitted meanings for this workflow: evidence received, settlement unconfirmed, partially settled and settlement confirmed. These are the fictional organisation's approved operational states, not universal accounting rules supplied by the developer.
Correct the rule and the affected record
The authorised change makes receipt of an attachment record evidence received. It leaves settlement unconfirmed until the required review is completed by the permitted role. The interface shows the reference and source of that decision separately from the customer message.
For I-72, staff retain F-41 and A-19, record why the automatic paid label was withdrawn and attach the bounded B-80 review. They do not delete the customer's document or rewrite it as a failed payment. Any downstream action that depended on the old status needs assessment by the responsible business owner; the software should not decide whether goods should be dispatched or a customer should be contacted.
The test submission of another advice document now records its receipt without changing settlement to confirmed. An ordinary content editor cannot authorise the settlement transition. These checks demonstrate the repaired rule, not merely a manual correction to I-72.
Follow the later evidence to an actual result
In the next authorised review, bank record B-82 shows a credit of 1,250.50 BAM. The reviewer matches the relevant account, reference and other required details to I-72 under the organisation's procedure. The worked result is settlement confirmed, with B-82 and the review decision linked to it. The system retains the earlier evidence-received event and the period during which settlement was unconfirmed.
Two controls prevent the repair from becoming another overbroad rule. Invoice I-73 requires 800.00 BAM and has a verified credit of 500.00 BAM; its approved state remains partially settled. A separate credit with no sufficiently established invoice match remains in review. A matching amount alone does not allocate it to whichever invoice is convenient.
This example concerns the evidence used by a business workflow. Actual accounting treatment, reconciliation procedures, customer communications and commercial consequences must be determined by your responsible team and advisers.
Review local formats without confusing them with authority
Bosnian-facing forms should be reviewed with representative names, addresses, dates, amounts and references. Check the entered information, stored record, staff view and any approved export. A value that looks right on the first screen may still become ambiguous later.
The Central Bank of Bosnia and Herzegovina identifies the convertible mark using the currency code BAM. Unicode's Bosnian locale data provides formatting reference material. Your project should still agree the exact permitted input and displayed price basis. Formatting a value is different from converting a currency, approving an invoice or confirming receipt of money.
Likewise, a provider's ability to display a currency does not establish that it will accept your merchant entity or support the required transaction. Confirm the actual account, service, approval and supported test arrangement before promising an online payment feature. A payment-related form may be useful without initiating a payment at all.
Keep the information request proportionate
Collect only what the defined follow-up task needs. A public project-enquiry form is not a place for bank credentials, card details or customer financial files. If a business workflow needs remittance evidence, agree the collection channel, access, retention and review responsibilities before adding it.
The useful acceptance record shows which event was received, which evidence was inspected and who was authorised to decide. It should let the next colleague distinguish an unanswered question from a confirmed outcome. Quote-intake planning and internal workflow development can apply that discipline to the surrounding customer process.