Invoice and payment status

Use the payable system’s result

The portal imports invoice status from the owning AP system. Preserve its source invoice identity, revision, currency, confirmed due date, original amount and open balance. The observed timestamp tells the supplier when that information was received. A display label is not a second editable payable ledger.

Received, under review, approved, scheduled and paid describe different stages. An invoice can be approved while no payment instruction has been sent. The portal must not convert approval into an expected bank settlement or replace a missing source balance with its own guess.

Keep the latest observation identifiable

Incoming snapshots retain their earlier versions so a question can be traced to the state a supplier saw. Only the current reconciled source revision appears as the active status. Duplicate or older events cannot overwrite a newer confirmed result merely because they arrive later.

Where the source does not provide a comparable revision, the configured connector must reconcile current state before promoting the update. Conflicting responses stay an integration exception. The portal reports that the latest observation is unavailable or stale instead of treating a successful network response as current financial truth.

Distinguish scheduled payment from settlement

Payment status records its source instruction, currency, amount, observed date and any expected payment date. Scheduled or submitted instructions remain distinct from pending bank activity and confirmed settlement. A supplier can use the expected date for planning while understanding it is conditional on the buyer’s actual payment process.

Only the verified settled source result supplies a settlement time. Failed, unknown and reversed outcomes retain their real state. A timeout must not mark an instruction paid or cause a new payment request; this portal observes the buyer’s execution and does not independently send money.

Explain which invoices a payment covers

A payment can allocate to several invoices. Retain the source allocation amount and any observed realised discount against each invoice identity. Keep planned cash, settled cash and realised discount distinct. Settled cash of 980 plus confirmed discount 20 relieves 1000 of the payable while bank settlement remains 980. Current cash allocations and unallocated cash reconcile to gross settlement less confirmed cash reversals; an older snapshot cannot be counted again. All allocations share the payment’s buyer, vendor and currency. Similar invoice numbers across suppliers are not a valid match.

The remittance document belongs to that observed payment and retains its file digest. It may explain the buyer’s intended payment composition before settlement, but it does not itself prove that funds arrived. The portal should show the associated payment state and protect the file under the same vendor membership.

Keep questions grounded in the observation

A supplier can open a case from an invoice or payment, preserving the source identity they are asking about. AP staff can compare the latest result with the earlier snapshot and investigate in the owning system. The response should identify whether the issue is invoice review, payment scheduling, settlement or a reversal. That keeps a status enquiry actionable without giving supplier users access to buyer bank credentials or unrelated financial records.