Payments · Video & transcript
The payment explained: which invoices did it cover?
A bounded investigation with Penny: inspect the evidence, decisions and follow-through in the film’s full narration.
Full narration available
White paper · Payments
A practical guide to payment preparation, release authority, changing cash assumptions, bank responses and evidence of completion.
Payment automation should connect an approved obligation to an authorized instruction, the bank’s response and the accounting result. Each state needs its own evidence. A reliable workflow keeps changed details, unavailable funds and uncertain outcomes visible so people can make the decisions that still need their authority.
An approved supplier invoice establishes an obligation within the approval process. It does not establish that the payment instruction is correct, the funding account has sufficient available money, or the bank has completed a transfer. Those are related checks with different evidence and responsibilities.
Proper’s character model makes the handoffs easy to explain: Billie handles accounts payable obligations, Payton handles payroll inputs and results, Penny handles controlled money movement, and Glen connects the accounting records. Use that distinction when mapping your own workflow. Name the owner of every handoff, the record received and the response that confirms the next stage.
A useful payment proposal brings together the approved amount, payee, checked payment details, funding account, method, relevant deadline and any expected fees. The reviewer should not need to reconstruct the proposal from scattered bank screens and messages. Preserve the source obligation so a change can be traced back to the item being paid.
The proposed batch is also a place to expose exceptions. A changed payee record, a missing authorization or an unresolved funding question should have a reason and a responsible person. Separate items that can progress under the business’s rules from items that require a decision. Putting everything into the same generic “ready” bucket makes the approval less meaningful.
A person may approve an invoice before the payment date, bank details or funding account are finalized. Establish which later changes require another decision. Approval should describe the action it authorizes closely enough that the release operator can tell whether it is still current.
For a changed supplier-bank instruction, retain the original request, the verification work and the final authorized details. Follow the organization’s established verification process. A convincing email or a familiar logo does not by itself establish that the new destination is correct. In a demonstration, ask how the held item is prevented from slipping into an otherwise approved batch.
A payment sequence depends on when money is available, where it is held and which obligations need that account. An expected customer receipt can influence a forecast but should remain visibly distinct from actual funds. If a receipt slips, determine which planned payments relied on it before deciding what can proceed.
Consider a synthetic planning example: an operating account has $65,000 available, payroll requires $50,000, and a proposed supplier payment is $20,000. Paying both from that account would require $70,000. A forecast receipt cannot remove the $5,000 gap until the applicable funding evidence supports it. The example illustrates dependency checking, not a recommendation to delay any particular obligation.
Bring real dates, contractual requirements, bank cutoffs and authorized alternatives into the decision. A future receipt arriving after a deadline does not solve the earlier problem. Money in a separate account is not automatically available for transfer. If no authorized feasible sequence exists, the useful result is a visible gap and an escalated decision.
After release, retain the response from the relevant payment system or bank. Distinguish an instruction accepted for processing from a completed transfer and from a reconciled accounting result. Use the provider’s actual states and explain how they map to the language shown to the team.
An uncertain response needs investigation. Sending the same instruction again without establishing what happened can create a second payment. Ask how the workflow identifies an existing instruction, checks its status and decides whether a retry is safe. A visible unresolved state is more useful than a false completion badge or an unexplained automatic resubmission.
Proper’s current Penny AI Now film, “The Payment Explained,” illustrates a supplier chasing an invoice that has already been included in a payment. Different references connect one payment with three invoices. Penny gathers the proof and prepares a reply; the person approves it and the supplier confirms. The illustrated $8,400 is example data, not a measured saving.
This story highlights a different kind of payment work: explaining a completed transaction. A bank debit alone may not explain the allocation the supplier needs. Connect the bank evidence with the payment batch, remittance and invoice references. The outcome is a supported explanation and acknowledged resolution, while the accounting history remains available.
Alto’s Payments AI Wow is a future concept about maintaining payment decisions as conditions change. Its value proposition concerns ongoing coordination across connected funds, obligations and approvals. It should be evaluated through the dependencies it follows and the actions it can actually complete under authorized rules.
Ask what happens when a receipt is late, an amount changes after approval or a bank outcome remains unknown. The system should identify the affected decisions, preserve unaffected work and show the person what now requires attention. Confirm current product scope separately; a film’s creative approval is not evidence that the portrayed workflow is released.
Build a small demonstration set around your actual payment methods and accounting connections. Include a routine batch, a changed payee detail, an unavailable funding assumption, an ambiguous bank response and a supplier asking for proof. Record the configuration and any manual steps needed to produce a trustworthy result.
Evaluate the evidence left behind as carefully as the initial screen. A colleague should be able to understand what was proposed, who authorized it, what was submitted, what the bank reported and how the ledger was reconciled. That record is what makes the workflow explainable when a payment is questioned later.
They are different decisions. The invoice supports an obligation; a payment authorization covers the instruction and relevant release conditions. Your process determines the required roles and checks.
Submission confirms that an instruction was sent or accepted at a particular stage. Later evidence establishes the money movement and its accounting treatment. Ask how the selected provider reports each state.
It can carry routine work within configured rules. Consequential decisions, changed instructions and unresolved exceptions still need the authority your organization assigns. Confirm the exact available controls in the product.
Bring your records, exceptions and the decisions that matter to your team.