ayelıne

Edge cases and states

The promise holds when things go wrong.

“Nothing moves above the line without a person” has to survive slow vendors, busy people, conflicting rules and broken integrations. Each case: when it happens, what people see, the exact words.

Sample data

Payment statuses

Seven statuses plus two event labels (refund, duplicate). Each has an icon, a word and one sentence of meaning. Color is the third signal, never the only one.

  • Paid · within pact

    Inside the pact. Paid, receipt matched, no person needed.

  • Held · needs a person

    Above the line. Waiting for a person; no money has moved.

  • Declined

    A person said no. The agent was told why.

  • Adjusted

    A person changed the terms; the agent went back to the vendor.

  • Blocked · never allowed

    Never allowed by the pact (e.g. gift cards). Not even asked.

  • Waiting for vendor

    Approved; waiting for the vendor to accept or invoice.

  • Declined · nobody decided

    Timed out after 4 h with owner and backup asked. Shown separately from a person’s no.

  • Refunded

    Money came back; matched to the original payment automatically.

  • Duplicate caught

    Same vendor, same amount within 10 min. Second one held for a person.

Hard decisions

Cases found while mapping the flows. Each one has a clear default, and each one is reachable in the demo.

  • Vendor rejects the adjusted terms

    When: Emily adjusted to a trial; Halden says annual only.

    Halden won’t offer a trial

    The request is back with you. Nothing was paid. Options: approve the original annual contract, or decline and the agent looks for another vendor.

    See it in the demo : Vendor rejects the adjusted terms
  • Owner is away

    When: Emily is on holiday; the Procurement agent asks for something above the line.

    Sent to Marcus (backup) · Emily is away until 18 Nov

    Backups are required for every agent, so requests never wait on one inbox. Emily sees what Marcus decided when she’s back.

    See it in the demo : Owner is away
  • Two rules disagree

    When: A renewal is “allowed under $5,000” but the vendor is on the “ask first” list.

    Two rules apply. The stricter one wins: asks a person.

    Shown in the request with both rules quoted, plus a link to fix the pact so it doesn’t happen again.

    See it in the demo : Two rules disagree
  • Price changes after approval

    When: Emily approved $1,530.00 a month; the invoice says $1,640.00.

    Invoice is 7% higher than approved

    Above the 5% tolerance, so it’s held again with the difference highlighted. Under 5%, it’s paid and noted.

    See it in the demo : Price changes after approval
  • Purse is empty

    When: The Cloud agent has spent its $40,000.00 monthly purse on the 27th.

    Cloud agent’s purse is empty for November

    New payments are held, not lost. Rachel can top up once, raise the limit, or let it wait for 1 December.

    See it in the demo : Purse is empty
  • Agent repeats a declined request

    When: The Procurement agent asks for the same Halden contract the next day.

    Blocked: same request was declined on 12 Nov

    Not sent to Emily again. The agent receives the original reason. A new request with different terms is treated as new.

    See it in the demo : Agent repeats a declined request

When something goes wrong

Loading, empty and error states keep the same promise: if Ayeline can’t check a payment, the payment waits.

Fieldstone Supply Co., its people and vendors are fictional.